RISC-V: Trim language around the CHERI ISA being a design space. #78
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CHERI-RISC-V's definition is more concrete with fewer alternatives than when the specification was first written. The only remaining design space choice is 32-bit vs 64-bit which is probably not enough to justify the remaining language. This does still keep the idea of a design space in the list of goals motivating the initial desire to apply CHERI to RISC-V as that list is largely historical.
|
I suspect Robert is unlikely to review this before the end of the month (when we'd like to have V9 ready). I believe this is inline with the pitch we wish to use for V9 though. |
brooksdavis
approved these changes
Jul 21, 2023
|
FWIW, when I was reading through, this section doesn't make sense (the list of one item is referred to in the plural) so can't be left as is. I would definitely just remove it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CHERI-RISC-V's definition is more concrete with fewer alternatives than when the specification was first written. The only remaining design space choice is 32-bit vs 64-bit which is probably not enough to justify the remaining language. This does still keep the idea of a design space in the list of goals motivating the initial desire to apply CHERI to RISC-V as that list is largely historical.